Enumeration of rooted partial subtrees

ABSTRACT

Embodiments of methods, apparatuses, devices and/or systems for manipulating hierarchical sets of data are disclosed. In particular, methods, apparatus devices and or/or systems for enumerating rooted partial subtrees are disclosed.

BACKGROUND

This disclosure is related to hierarchical data arrangements and, more particularly, to manipulating such data arrangements.

In a variety of fields, data or a set of data, may be represented in a hierarchical fashion. This form of representation may, for example, convey information, such as particular relationships between particular pieces of data and the like. However, manipulating such data representations is not straight-forward, particularly where the data is arranged in a complex hierarchy. Without loss of generality, one example may include a relational database. Techniques for performing operations on such a database, for example, are computationally complex or otherwise cumbersome. A continuing need, therefore, exists for additional techniques for manipulating data hierarchies.

BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. The claimed subject matter, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference of the following detailed description when read with the accompanying drawings in which:

FIG. 1 is a schematic diagram of one embodiment of a tree;

FIG. 2 is a schematic diagram illustrating one embodiment of a binary edge labeled tree (BELT);

FIG. 3 is a schematic diagram illustrating another embodiment of a BELT;

FIG. 4 is a table illustrating a particular embodiment of an association between natural numerals and BELTS;

FIG. 5 is a table illustrating a portion of the Kleene enumeration of non-composite numerals;

FIG. 6 is a schematic diagram of an embodiment of a node labeled tree;

FIG. 7 is a schematic diagram illustrating another embodiment of a node labeled tree;

FIGS. 8 through 11 are schematic diagrams illustrating, by way of example, rooted partial subtrees (RPSTs) according to an embodiment.

FIG. 12 is a flow diagram illustrating a process to enumerate RPSTs from a tree according to an embodiment.

FIG. 13 is a schematic diagram illustrating a generalized representation of an embodiment of a subtree according to an embodiment,

FIGS. 14 and 15 are schematic diagrams illustrating applications of one embodiment of a push operation according to an embodiment.

FIGS. 16, 17 and 18 are flow diagrams illustrating a process to enumerate RPSTs from a tree according to an embodiment.

FIGS. 19 through 28 are schematic diagrams illustrating, by way of example, a process to enumerate RPSTs from a tree according to an embodiment.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the claimed subject matter. However, it will be understood by those skilled in the art that the claimed subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components and/or circuits have not been described in detail so as not to obscure the claimed subject matter.

Some portions of the detailed description which follow are presented in terms of algorithms and/or symbolic representations of operations on data bits or binary digital signals stored within a computing system memory, such as a computer memory. These algorithmic descriptions and/or representations are the techniques used by those of ordinary skill in the data processing arts to convey the substance of their work to others skilled in the art. An algorithm is here, and generally, considered to be a self-consistent sequence of operations and/or similar processing leading to a desired result. The operations and/or processing involve physical manipulations of physical quantities. Typically, although not necessarily, these quantities may take the form of electrical and/or magnetic signals capable of being stored, transferred, combined, compared and/or otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals and/or the like. It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining” and/or the like refer to the actions and/or processes of a computing platform, such as a computer or a similar electronic computing device, that manipulates and/or transforms data represented as physical electronic and/or magnetic quantities within the computing platform's memories, registers, and/or other information storage, transmission, and/or display devices.

In a variety of fields, data or sets of data may be represented in a hierarchical fashion. This form of representation may, for example, convey information, such as particular relationships between particular pieces of data and the like. However, manipulating such data representations is not straight forward, particularly where the data is arranged in a complex hierarchy. Without loss of generality, one example may include a relational data base. Techniques for performing operations on such a data base for example, may be computationally complex or otherwise cumbersome. A continuing need, therefore, exists for additional techniques for manipulating data hierarchies.

As previously discussed, in a variety of fields, it is convenient or desirable to represent data, a set of data and/or other information in a hierarchical fashion. In this context, such a hierarchy of data shall be referred to as a “tree.” In a particular embodiment, a tree may comprise a finite, rooted, connected, unordered, acyclic graph. This is illustrated here, for example, in FIG. 1 by embodiment 100. As illustrated, the root of this particular embodiment encompasses node 105. In addition to 105, there are eight other nodes designated 110 to 140, respectively. Likewise, the nodes are connected by branches referred to, in this context, as edges. Thus, the nodes of this tree are connected by eight edges. This embodiment, therefore, illustrates a finite tree that is rooted by node 105. Furthermore, the nodes are connected, meaning, in this context, that a path exists between any two nodes of the tree. The tree is likewise acyclic, meaning here, that no path in the tree forms a complete loop. Here, unordered refers to the notion that there is no implied ordering or precedence among nodes attached to a common node, despite the appearance of ordering in a graphical illustration.

As previously suggested, in a variety of contexts, it may be convenient and/or desirable to represent a hierarchy of data and/or other information using a structure, such as the embodiment illustrated in FIG. 1 . One particular embodiment, without loss of generality, of a tree may include edges that are labeled with data and/or other values. Likewise, in one particular embodiment, such data or values may be limited to binary data, that is, in this example, either a binary one or a binary zero. Here, such an embodiment may be referred to as a binary edge labeled tree (BELT), as shall be discussed in more detail hereinafter.

One example of a BELT is illustrated by embodiment 200 of FIG. 2 . Thus, as illustrated, the edges of the BELT shown in FIG. 2 are labeled with either a binary zero or binary one. FIG. 3 illustrates another embodiment 300 of a different binary edge labeled tree. It is noted that this tree is similar to the embodiment of FIG. 2 . Without belaboring the present discussion, additional descriptions of how BELTs may represent a hierarchy of, data may be found in U.S. patent application Ser. No. 11/005,859, filed on Dec. 6, 2004, by J. J. LeTourneau, titled, “Manipulating Sets of Hierarchical Data,” assigned to the assignee of the presently claimed subject matter.

Binary edge labeled trees may also be enumerated. Thus, for this particular embodiment, although the claimed subject matter is not limited in scope in this respect, a method of enumerating a set of trees begins with enumeration of an empty binary edge labeled tree and a one node binary edge labeled tree. Here, the empty tree is associated with the zero and has a symbolic representation as illustrated in FIG. 4 (circle). Likewise, the one node tree, which holds no data, is associated with the numeral one and has a graphical representation of a single node. For higher positive natural numerals, however, this embodiment of a method of enumerating a set of trees comprises positioning a tree at location k, k being a positive numeral greater than three, where k is the product of u and v, u and v comprising positive numerals greater than one, such that the tree is formed by a union of the trees at positions u and v. Likewise, for those locations that are not a product of other natural positive numerals greater than one, that is, for locations that comprise non-composite numerals, denoted here by j, for example, j being a positive natural numeral greater than one, a tree is positioned at location j such that the tree is formed by finding the first tree in the prior enumeration such that the binary edge labeled tree obtainable from this first tree by attaching a node to the particular tree as a new root node and labeling the edge between the new root node and the prior root node with a binary “0” label is not in the enumeration at some position lower than j; however, if the binary edge labeled tree obtainable from that first tree, as just described, is present in the enumeration with a binary “0” label for the new edge, but not with a binary “1” label, then the tree at position j is that tree with a binary 1” label for the new edge. This may be illustrated, for example in FIG. 4 , as described in more detail below.

However, for this particular embodiment, although the claimed subject matter is not limited in scope in this respect, a method of enumerating a set of ordered trees may begin with enumeration of an empty binary edge labeled tree and a one node binary edge labeled tree. Thus, the empty tree is associated with the zero and has a symbolic representation as illustrated in FIG. 4 (circle). Likewise, the one node tree, which holds no data, is associated with the numeral one and has a graphical representation of a single node. For higher positive natural numerals, ordered trees may be generated by a process described, for example, in “The Lexicographic Generation of Ordered Trees,” by S. Zaks, The Journal of Theoretical Computer Science, Vol. 10(1), pp. 63-82, 1980, or Enumerating Ordered Trees Lexicographically,” by M. C. Er, Computation Journal, Vol. 28, Issue 5, pp. 538-542, 1985.

As illustrated, for this particular embodiment, and as previously described, the empty tree has zero nodes and is associated with the numeral zero. Likewise, the one node tree root comprises a single node and is associated with the numeral one. Thus, to obtain the tree at position two, a root node is attached and connected to the prior root node by an edge. Likewise, here, by convention, the edge is labeled with a binary zero. If, however, the tree formed by the immediately proceeding approach were present in the prior enumeration of trees, then a similar process embodiment is followed, but, instead, the new edge is labeled with a binary one rather than a binary zero. Thus, for example, in order to obtain the binary edge labeled tree for position three, a new root node is connected to the root node by an edge and that edge is labeled with a binary one.

Continuing with this example, to obtain the binary edge labeled tree for position four, observe that numeral four is the product of numeral two times numeral two. Thus, a union is formed at the root of two trees, where, here, each of those trees is associated with the positive natural numeral two. Likewise, to obtain the binary edge labeled tree for position five, begin with the binary edge labeled tree for position two and follow the previously articulated approach of adding a root and an edge and labeling it with a binary zero.

In this context, adding a root node and an edge and labeling it binary zero is referred to as a “zero-push” operation and adding a root node and an edge and labeling it binary one is referred to as a “one-push” operation. Based at least in part on the prior description, for this particular embodiment, it may now be demonstrated that if k is any positive natural numeral and a tree x is positioned at location k, then a non-composite numeral is associated with the zero-push of that tree and a non-composite numeral is associated with the one-push for that tree. Furthermore, the non-composite index of the zero-push of the tree comprises 2k−1, whereas the non-composite index of the one-push of the tree comprises 2k, where the index corresponds to the argument of the well-known Kleene enumeration on positive natural numerals of non-composite numerals, as illustrated, for example, in part in FIG. 5 . Thus, referring again to FIG. 4 , the one-push of the root tree is the tree at position three. This follows from FIG. 5 since P(2*1)=P(2)=3. Likewise, the tree at position five is the zero-push of the tree at position 2. Again, this follows from FIG. 5 since P(2*2−1)=P(3)=5.

In this context, the approach just described may be referred to as vectorizing non-composite numerals. In the embodiment just described, this was accomplished in pairs, although, of course, the claimed subject matter is not limited in scope in this respect. This may be accomplished in any number of numeral combinations, such as triplets, quadruplets, etc. Thus, using a quadruplet example, it is possible to construct trees such that if k is any positive natural numeral and a tree x is positioned at location k, then a non-composite numeral is associated with the zero-push of that tree, a non-composite numeral is associated with the one-push for that tree, a non-composite numeral is associated with the two-push for that tree, and a non-composite number is associated with the three-push for that tree. Furthermore, the index of the non-composite numeral is such that for a zero-push of the tree, the index comprises (4k−3), for a one-push of a tree, the index comprises (4k−2), for a two-push of a tree, the index comprises (4k−1), and for a three-push of a tree the index comprise (4k), where the index corresponds to the kleene enumeration of non-composite numerals, P(index), such as provided in FIG. 5 .

In the previously described enumeration of binary edged labeled trees, a mechanism may be employed to reduce or convert complex manipulations of hierarchical data to multiplication of natural numerals. For example, if it is desired to combine, or merge at their roots, two trees of hierarchical data, a complex task both computationally and graphically, instead, for this particular embodiment, the two trees may be converted to numerical data by using the previously described association embodiment between binary edge labeled trees and natural numerals. The resulting numerical data from the prior conversion may then be multiplied, and the resulting product may then be converted to a binary edge labeled tree by using a table look up of the previously described association embodiment. It is noted that a subtle distinction may be made between an enumeration embodiment and an association embodiment. Enumeration may comprise listing, in this example, a particular ordered embodiment of BELTs, whereas an association provides a relationship between, in this example, a particular ordered embodiment of BELTs and natural numerals. It is, of course, appreciated that many different enumeration and association embodiments may be employed to execute the operations discussed above Sand hereinafter, and the claimed subject matter is intended to cover all such enumeration and association embodiments.

Likewise, a process embodiment that is a reversal to the previously described embodiments may also be employed. Thus, complex hierarchies of data may be split or divided, when this is desired. For example, a binary edge labeled tree to be divided may be converted to a piece of numerical data, such as by using the previously described association embodiment. This data may then be factored into two pieces of numerical data whose product produces the previously mentioned piece of numerical data. These two pieces of numerical data may then be converted to trees, again, by using the prior association embodiment, for example.

Another form of manipulating hierarchical sets of data may involve ordering or hashing. This may be desirable for any one of a number of different operations to be performed on the sets of data. One approach is similar to the previously described embodiment. For example, it may be desired to order a given set of trees. Doing so may involve converting the trees to numerical data, as previously described, using an association embodiment. The numerical data may then be ordered and the numerical data may then be converted back to binary edge labeled trees using the previously described association embodiment, or an alternate association embodiment, for example.

It is noted that there may be any one of a number of different ways of converting from numerals or numerical data values to a binary edge labeled tree or from a binary string to a binary edge labeled tree, and vice-versa. Nonetheless, a convenient method for doing so with this particular embodiment includes storing a table providing an association embodiment between natural numerals, binary strings and binary edge labeled trees, such as the embodiment previously described. Thus, once it is desired to convert from one to the other, such as from a binary string to a BELT, from a natural numeral to a BELT, or vice-versa, for example, a table look up operation may be performed using the association embodiment.

Techniques for performing table look ups are well-known and well-understood. Thus, this will not be discussed in detail here. However, it shall be appreciated that any and all of the previously described and/or later described processing, operations, conversions, transformations, manipulations, etc. of strings, trees, numerals, data, etc. may be performed on one or more computing platforms or similar computing devices, such as those that may include a memory to store a table as just described, although, the claimed subject matter is not necessarily limited in scope to this particular approach. Thus, for example, a hierarchy of data may be formed by combining two or more hierarchies of data, such as by applying a previously described embodiment. Likewise, multiple hierarchies of data may be formed by splitting or dividing a particular hierarchy of data, again, such as by applying a previously described embodiment. Likewise, additional operations and/or manipulations of data hierarchies may be performed, such as ordering hierarchies of data and more. It is intended that the claimed subject matter cover such embodiments.

Much of the prior discussion was provided in the context of binary edge labeled trees. Nonetheless, as alluded to previously, binary edge labeled trees and binary node labeled trees may be employed nearly interchangeably to represent substantially the same hierarchy of data. In particular, a binary node labeled tree may be associated with a binary edge labeled tree where the nodes of the binary node labeled tree take the same values as the edges of the binary edge labeled tree, except that the root node of the binary node labeled tree may comprise a node having a zero value or a null value. Thus, rather than employing binary edge labeled trees, the previously described embodiments may alternatively be performed using binary node labeled trees. As one example embodiment, operations and/or manipulations may be employed using binary edge labeled trees and then the resulting binary edge labeled tree may be converted to a binary node labeled tree. However, in another embodiment, operations and/or manipulations may be performed directly using binary node labeled trees where a different association embodiment, that is, in this example, one that employs binary node labeled trees, is employed.

In accordance with the claimed subject matter, therefore, any tree, regardless of whether it is binary edge labeled, binary node labeled, non-binary, a feature tree, or otherwise, may be manipulated and/or operated upon in a manner similar to the approach of the previously described embodiments. Typically, different association embodiments shall be employed, depending at least in part, for example, upon the particular type of tree. For example, and as shall be described in more detail below in connection with FIG. 6 , a node labeled tree in which the nodes are labeled with natural numerals or data values may be converted to a binary edge labeled tree. Furthermore, this may be accomplished with approximately the same amount of storage. For example, for this particular embodiment, this may involve substantially the same amount of node and/or edge data label values.

As previously noted, the claimed subject matter is not limited in scope to this particular example, however, as illustrated in more detail hereinafter, the tree illustrated in FIG. 6 is converted to a binary edge labeled tree through a sequence of processing depicted here as graph operations, although such a conversion may alternatively be implemented by operations implemented otherwise, one such example being a computing platform, for example. Alternatively, it may be desirable, depending upon the particular embodiment, to convert trees to, for example binary node labeled trees. Likewise, other embodiments in which trees of one form are converted to trees of another form are also included within the scope of the claimed subject. However, for this particular embodiment, it will be assumed that the association between trees and numerals, such as previously described, is depicted or enumerated in terms of binary edge labeled trees, as previously illustrated, for example. Thus, in this example, a particular tree, embodiment 1100, is illustrated in FIG. 6 , comprises a node labeled tree rather than an edge labeled tree. Without belaboring the present discussion, a process of converting a node labeled tree such as that illustrated in FIG. 6 to a BELT may be found in U.S. patent application Ser. No. 11/005,859 filed on Dec. 6, 2004, by J. J. LeTournesu, titled, “Manipulating Sets of Hierarchical Data,” assigned to the assignee of the presently claimed subject matter.

In another embodiment, however, a particular tree may include null types or, more particularly, some node values denoted by the empty set. This is illustrated, for example, by the tree in FIG. 7 , although, of course, this is simply one example. An advantage of employing null types includes the ability to address a broader array of hierarchical data sets. For example, without loss of generality and not intending to limit the scope of the claimed subject matter in any way, a null type permits representing in a relational database, as one example, situations where a particular attribute does not exist. As may be appreciated, this is different from a situation, for example, where a particular attribute may take on a numeral value of zero. Thus, it may be desirable to be able to address both situations when representing, operating upon and/or manipulating hierarchical sets of data. A tree with nulls may be converted to a tree without nulls as described in U.S. patent application Ser. No. 11/005,859, filed on Dec. 6, 2004, by J. J. LeTourneau, titled, “Manipulating Sets of Hierarchical Data,” assigned to the assignee of the presently claimed subject matter.

Likewise, in an alternative embodiment, a node labeled tree may comprise fixed length tuples of numerals. For such an embodiment, such multiple numerals may be combined into a single numeral, such as by employing Cantor pairing operations, for example. See, for example, Logical Number Theory, An Introduction, by Craig Smorynski, pp, 14-23, available from Springer-Verlag, 1991. This approach should produce a tree to which the previously described embodiments may then be applied. Furthermore, for one embodiment, a tree in which nodes are labeled with numerals or numerical data, rather than binary data, may be converted to a binary edge labeled tree and/or binary node labeled tree, and, for another embodiment, a tree in which edges are labeled with numerals or numerical data, rather than binary data, may be converted to a binary edge labeled tree and/or binary node labeled tree.

Furthermore, a tree in which both the nodes and the edges are labeled may be referred to in this context as a feature tree and may be converted to a binary edge labeled tree and/or binary node labeled tree. For example, without intending to limit the scope of the claimed subject matter, in one approach, a feature tree may be converted by converting any labeled node with its labeled outgoing edge to an ordered pair of labels for the particular node. Using the embodiment described above, this tree may then be converted to a binary edge labeled tree.

In yet another embodiment, for trees in which data labels do not comprise simply natural numerals, such as, as one example, trees that include negative numerals, such data labels may be converted to an ordered pair of numerals. For example, the first numeral may represent a data type. Examples include a data type such as negative, dollars, etc. As described above, such trees may also be converted to binary edge labeled trees, such as by applying the previously described embodiment, for example.

As previously described, trees may be employed to graphically represent a hierarchy of data or a hierarchy of a set of data. This has been illustrated in some detail for binary edge labeled trees, for example. As the previous figures, illustrate, however, such graphical hierarchical representations typically employ two spatial dimensions to depict the relationship among different pieces of data. This may be disadvantageous in some situations where a one dimensional representation or arrangement of symbols, such as is employed with alphabetic letters, for example, that are combined to create a linear collection of successive symbols or notations, such as words, would be more convenient.

According to an embodiment, a tree may be expressed as one or more “subtrees” merged at the root node of the tree. A subtree is coupled to the root node of the tree at an edge and independently has properties of a tree, except that the subtree is part of a larger tree. For example, here, a subtree comprises at least a “root” node coupled by an edge to a root node of the larger tree. Additional nodes and edges may be coupled to the root node of the subtree. While a subtree may comprise an edge coupled to the root node of the tree, the size and shape of the subtree may express information like that of a tree having the same size and shape as the subtree. The subtrees merged together at the root node of a tree may be referred to as “subtree children” of the tree node and any particular one of such subtrees may be referred to as a “subtree child” of the tree in this embodiment. Also, like a tree, a subtree may be represented as a natural numeral according to an association of trees with natural numerals as illustrated with reference to FIG. 4 , for example. The subtrees making up a larger tree may be enumerated from a finite number of nodes according to a process described in U.S. patent application Ser. No. 11/006,440, filed on Dec. 6, 2004, by Karl Schiffmann, LeTourneau, titled, “Enumeration of Trees from a Finite Number of Nodes,” assigned to the assignee of the presently claimed subject matter. However, the claimed subject matter is not limited in this respect.

According to an embodiment, a tree having a root node may be comprise one or more “rooted partial subtrees” (RPSTs) representing at least a portion of the hierarchical data represented by the tree. In this particular embodiment, a component RPST of a tree may comprise the same root node as the full tree, one or more other nodes in the tree coupled to the root node by intermediate nodes, the intermediate nodes themselves, and edges in the tree coupling the root node, the one or more other nodes and the intermediate nodes to one another. A component RPST of a full tree defines a connected path between the root node of the full tree and any other node in the component RPST along one or more edges in the tree, and any intermediate nodes. Accordingly, a component RPST may independently have properties of a tree, except that the RPST is part of a larger tree. Having properties of a tree, in a particular embodiment, a component RPST may comprise a finite, rooted, connected, unordered acyclic graph as illustrated with reference to FIGS. 1-7 . As such, in a particular embodiment, any labels associated with nodes and edges in the full tree may also be associated with corresponding nodes and edges in any component RPST. Also, in a particular embodiment, such a component RPST may be represented by a natural numeral according to an association of natural numerals and trees as illustrated above with reference to FIG. 4 , for example.

While a subtree and RPST of a full tree may represent portions of a graphical representation of the full tree and/or hierarchical data expressed in the full tree, properties of a subtree and RPST may be distinguished. In a particular embodiment, if the RPST comprises a child node coupled to the root node of the full tree, the RPST need not include all nodes and edges depending from the child node. Also, an RPST may comprise two or more child nodes connected to the root node of the full tree by respective edges. However, these are merely examples of properties that may distinguish an RPST from a subtree in a particular embodiment, and the claimed subject matter is not limited in this respect.

Since a tree is finite, there are a finite number of paths between a root node of the tree and any other node in the tree. Similarly, there are a finite number of combinations of paths between the root node of a tree and individual ones of the other nodes in the tree. Accordingly, in a particular embodiment, a finite number of RPSTs may be enumerated from a tree having a root node. Natural numerals may be associated with the enumerated RPSTs based, at least in part, on an association between trees and natural numerals such as, for example, illustrated above with reference to FIG. 4 . However, this is merely an example embodiment and the claimed subject matter is not limited in this respect.

According to an embodiment, the enumerated RPSTs of a tree may be represented as a “set” containing a collection of unordered elements. In a particular embodiment, the elements of the set of enumerated RPSTs may contain as elements natural numerals representing individual ones of the enumerated RPSTs according to the aforementioned association between trees and natural numerals. The elements of such a set may be alternatively expressed as graphical representations of the individual ones of the enumerated RPSTs. In a particular embodiment, a one-to-one mapping may relate elements of the set of RPSTs expressed as natural numerals and elements of the set of RPSTs expressed as graphical representations. Here, such a mapping may enable converting graphical representations of RPSTs to corresponding natural numerals and manipulation of such natural numerals to provide resulting natural numerals. The resulting natural numerals may then be converted back to graphical representations. However, these are merely examples of how a set of enumerated RPSTs may be expressed and the claimed subject matter is not limited in these respects.

For a particular embodiment, a “full tree” is defined as an integral tree comprising all of its nodes, edges coupling the nodes to one another and any labels associated with the nodes or edges. Therefore, a full tree includes all of its nodes and elements completely connected. Also, such a full tree may be represented by a natural numeral denoted here as “FT.” The notation “{RPSTs::FT}” provides a shorthand notation for this particular embodiment to indicate the set of unique, unordered RPSTs that may be formed from a full tree “FT,” In one embodiment, the elements of {RPSTs::FT} may comprise natural numerals representing corresponding component RPSTs. As shown in FIGS. 8 through 11 , where FT represents tree 1200, elements of {RPSTs::FT} comprise the component RPSTs shown in FIGS. 9, 10 and 11 (among other component RPSTs as illustrated below).

FIG. 8 is a schematic diagram of a tree 1200 illustrating, by way of example, RPSTs of tree 1200. Tree 1200 comprises a root node 1202 and nodes 1204, 1206, 1208, 1210 and 1212 coupled to the root node 1202 by edges and intermediate nodes. In the presently illustrated embodiment, tree 1200 comprises a BELT. It should be understood, however, that other types of trees (either labeled trees or unlabeled structure trees) may similarly comprise RPSTs and that the claimed subject matter is not limited in this respect,

FIGS. 9, 10 and 11 are schematic diagrams of some RPSTs of tree 1200 according to an embodiment. These RPSTs include root node 1202 of tree 1200, at least one other node of tree 1200, and any edges or intermediate nodes in tree 1200 coupling the at least one other node to the root node 1202. However, it should also be understood that the set of RPSTs of tree 1200 may also include, for example, a single node 1202 or the full tree 1200. FIGS. 9 and 10 show RPSTs including root node 1202 and one other node in tree 1200 which connected via an edge in tree 1200 between root node 1202 and the one other node. FIG. 11 shows an RPST including root node 1202, nodes 1208, 1210 and 1212, and intermediate node 1206 coupling the root node 1202 to the nodes 1208, 1210 and 1212. It should be understood that FIGS. 9, 10 and 11 are merely examples of RPSTs that may be formed from tree 1200, and that these examples are not intended to provide an exhaustive enumeration of RPSTs that may be formed from tree 1200,

FIG. 12 is a flow diagram illustrating a process 1250 to enumerate RPSTs from a tree according to an embodiment. In this particular embodiment, the process 1250 may enumerate the RPSTs of full tree FT to define elements of {RPSTs::FT} as a result. FT may be represented as a natural numeral received at block 1252, {RPSTs::FT} may be initialized as the empty set at block 1254 to be subsequently filled with elements representing RPSTs enumerated in subsequent portions or process 1250.

According to an embodiment, the process 1250 recognizes that the full tree may represent any one of four different configurations: an empty tree; a single node tree; a tree comprising a single subtree connected to a root node of the full tree by an edge; and two or more subtrees connected to the root node of the full tree by respective edges. Accordingly, the process 1250 enumerates the RPSTs of the full tree based, at least in part, on the particular configuration of the full tree. Diamond 1256 determines whether FT represents an empty tree containing no nodes. If so, {RPSTs::FT} remains defined as the empty set and process 1250 terminates at block 1268. If diamond 1258 determines that FT contains a single node tree, block 1260 updates {RPSTs::FT} to include a natural numeral expressing a single node tree (here, {r}).

At diamond 1262 through block 1268, process 1250 enumerates RPSTs based, at least in part, on the configuration of the full tree as having either a single subtree connected to the root node of the full tree by an edge, or two or more subtrees connected to the root node by respective edges. If FT represents a single subtree connected to the root node of the full tree by an edge, block 1264 enumerates the RPSTs of the single subtree. Here, the RPSTs of the full tree may be determined, at least in part, from the RPSTs of the single subtree.

If FT represents a full tree having two or more subtrees connected to the root node of the tree by respective edges, block 1266 may enumerate the RPSTs of the individual ones of the two or more subtrees. At least some of the RPSTs of the full tree may be determined, at least in part, from RPSTs of the individual subtrees. Block 1266 may then enumerate additional RPSTs of the full tree based, at least in part, combinations of the enumerated RPSTs merged at the root node of the full tree.

According to an embodiment, blocks 1264 and 1266 may be carried out by recursive execution of at least a portion of the process 1250. At block 1264, for example, the single subtree of the full tree may itself comprise two or more subtree children connected by respective edges to a node. Block 1264 may execute portions of block 1266 to enumerate the RPSTs of the subtree based, at least in part, on RPSTs enumerated from individual ones of the subtree children of the single subtree. Similarly, block 1266 may enumerate RPSTs of individual ones of the subtrees connected to the root node of the full tree by executing portions of block 1264.

FIG. 13 is a schematic diagram illustrating a representation an embodiment of a subtree comprising an edge having a label “e” with a subtree root node having a label “n” where “e” and “n” may be represented by discrete values (e.g., Boolean, binary, integer, natural numeral and/or whole numeral values). A value associated with a “child tree” of the subtree may be represented by “x” which may represent information expressed as a natural numeral according to an association of natural numerals with trees as illustrated above with reference to FIG. 4 . Like a tree, subtree and RPST, such a child tree may have properties of a tree and be associated with a natural numeral according to an association between trees and natural numerals. However, this is merely an example of a representation of a subtree and its child tree, and the claimed subject matter is not limited in this respect.

As described below in connection with relation (1), a push operation may define a relationship between a subtree and a child tree of the subtree. As an association between trees and natural numerals may associate particular trees with natural numerals (e.g., as illustrated in FIG. 4 ), a push operation may define a relationship between a natural numeral associated with a subtree and a natural numeral associated with a child tree of the subtree. Similarly, a push operation may also define a relationship between natural numerals representing RPSTs of the child tree and natural numerals associated with at least some of the RPSTs of the subtree. A value of, or natural numeral associated with, the subtree shown in FIG. 13 may be expressed as the result of a push operation on the child tree having the value x. Such a push operation on the child tree may be represented in relation (1) as follows:

push(j,k,x)=P[kx+j−k+(2−r)], if j<k and k>0  (1)

where:

-   -   P(m)=Kleene enumeration function for generating a sequence of         non-composite numerals illustrated with reference to FIG. 5 ;     -   k=total number of values possible for a label;     -   j=actual computed label index value;     -   x=value of, or natural numeral associated with, “pushed” child         tree; and     -   r=defined value of tree system root/single node tree (e.g.         either 0 or 1).

It should be understood that while the push operation of relation (1) is suitable for performing specific embodiments described herein, this push operation is merely an example of how a push operation may be performed and the claimed subject matter is not limited in this respect. Additionally, it should be noted that the value of “r” is selected based upon a particular association of natural numerals and trees according to an association embodiment. Here, such an association of natural numerals may define a particular natural numeral to represent a tree comprising a single node. In the association of natural numeral with trees of FIG. 4 , for example, the single node is associated with “1” defining r=1. However, this is merely an example of how a natural numeral may represent a single node for a particular association embodiment and the claimed subject matter is not limited in this respect.

It should also be noted that “j” (the actual computed label index value associating the root node with the pushed subtree) is a function of the specific values of “e” (the specific edge label) and “n” (the specific node label). In the particular case of a BELT, for example, there may be no node values such that “j”=“e”. The value of “k” (total number of possible index values) may be determined as function of the possibilities of values of “e” (edge label value) and “n” (node label value) and, in a particular embodiment, “k” may be determined as the number of possibilities for “e” multiplied by the number of possibilities for “n.” Again, in the particular case of a BELT, “k” equals the number of possibilities for the value “e” since there are no node labels.

The techniques described herein for enumerating RPSTs of a full tree may be applied to any particular type of tree. For illustration purposes, particular examples described herein are directed to enumerating RPSTs of a BELT. Accordingly, while it is understood that an actual computed index value associating the root node with the pushed subtree may be determined from node labels (having a value “n”) and/or edge labels (having a value “e”), for simplicity the remaining discussion will denote the actual computed label index value “j” as an edge label value of an edge connecting a root node of a tree to a pushed child tree.

In enumerating at least some RPSTs of a tree based, at least in part, on enumerated RPSTs of a subtree of the RPST, it may be useful to express a push operation on multiple RPSTs in a single push operation. In addition to applying a push operation to a tree having a value x, the push operation may be applied to multiple trees or tree elements of a set (here, an unordered collection of elements representing trees, RPSTs, subtrees and/or child trees of a subtree) in relation (2) as follows:

push[j,k,{a,b,c}]={push(j,k,a)}U{push(j,k,b)}U{push(j,k,c)}  (2)

where a, b and c are numerical representations of tree elements in the pushed set. The result of the operation of relation (2) may be referred to as a “pushed set” of tree elements,

FIGS. 14 and 15 illustrate applications of the push operation of relation (1) to specific subtrees. FIG. 14 shows a BELT having a value of “2” according to the association of trees and natural numerals shown in FIG. 4 . As such, a push operation on this tree would define x=2, k=2 and r=1. FIG. 15 illustrates the result of a push of the tree in FIG. 14 by an edge having a label zero (i.e., a zero-push). The value of j for this push operation is zero. Accordingly, the push operation provides a numeral associated with the pushed BELT as follows:

push(j,k,x)=P[2*2+0−2+2−1]=P[3]=5.

It should be understood, however, the application of the push operation of relation (1) a BELT as illustrated in FIGS. 14 and 15 are merely particular examples of the push operation and the push operation may be similarly applied to non-BELT trees.

To enumerate RPSTs of a subtree of a full tree, it may be useful to determine a natural numeral associated with a child tree of the subtree based, at least in part, on a natural numeral associated with the subtree (the natural numerals being based, at least in part, on an association between trees and natural numerals). Like the push operation of relation (1), according to an embodiment, an “inverse push” operation may define a relationship between a subtree (e.g., a subtree of a parent full tree) and the child tree of the subtree (as illustrated in FIG. 13 ). Here, such an inverse push operation may define a relationship between natural numerals associated with such subtrees and natural numerals associated with respective child trees of such subtrees. Operating on such a natural numeral associated with a subtree (according to an association of trees with natural numerals as illustrated with reference to FIG. 4 , for example), an inverse push operation may provide a natural numeral associated with a child tree portion. In a particular embodiment, an inverse push operation may provide as a result as (1) a natural numeral representing a child tree (“Child”) and an edge label value linking the child tree with the root node of the parent full tree (“j”). For example, an inverse push operation on a tree may be represented in relation (3) as follows:

push⁻¹(r,k,ST)=<Child,j>

Child=Int[(P ⁻¹(ST)+k−(2−r))/k]; and

j=[P ⁻¹(ST)+k−(2−r)]modulo[k]   (3)

where:

-   -   P⁻¹(h)=an inverse of the Kleene enumeration function for         generating a sequence of non-composite numbers illustrated with         reference to FIG. 5 ;     -   ST=value of, or natural numeral associated with, subtree with         edge label value     -   Child=natural numeral representing child tree of subtree         represented by ST;     -   j=edge label value linking the child tree with the root node of         parent full tree;     -   k=total number of possible edge label index values linking the         child tree with the root node of parent full tree; and     -   r=defined value of tree system root/singleton node (either 0 or         1).

It should also be understood that the inverse push operation of relation (3) is merely an example of an inverse push operation used to determine a natural numeral associated with a child tree based, at least in part on a natural numeral associated with a parent subtree, and that the claimed subject matter is not limited in this respect. For example, for simplicity relation (3) assumes that information of a computed index value “j” associating the root node of the parent full tree and the child tree may be derived from edge label values in the absence of node label values (e.g., as in the case of a BELT). However, relation (3) may be expanded to apply to other non-BELT trees. Applied to the tree of FIG. 13 , for example, the inverse push operation of relation (3) may be expanded to yield a natural numeral representing the child tree as the value “x” and the label index value j (being a function of edge and node label values “e” and “n”).

In the particular embodiment of an inverse push operation illustrated in relation (3), the inverse Kleene enumeration function, P⁻¹(h), provides a result based upon ST (value of, or natural numeral associated with the subtree). Since the Kleene enumeration function generates non-composite natural numerals, the domain of P⁻¹(h) may be limited to non-composite natural numerals. In connection with the association of natural numerals and trees illustrated with reference to FIG. 4 , accordingly, the inverse push operation of relation (3) may be applied to natural numerals representing trees having a root node coupled to a single node (or having a single subtree). In one particular implementation of the inverse of the Kleene enumeration function, P⁻¹(h), a look-up table may associate values of h and P⁻¹(h) as shown in Table 1 as follows:

TABLE 1 h P⁻¹(h) 2 1 3 2 5 3 7 4 11 5 13 6 17 7 19 8 23 9 29 10 31 11 37 12 41 13 43 14 47 15 53 16 59 17 61 18 67 19 71 20 73 21 79 22 83 23

To enumerate at least some of the RPSTs of a full tree having two or more subtrees, it may be useful to determine combinations of RPSTs enumerated from the different subtrees. In the case of a full tree comprising two subtrees, in a particular example, individual elements of a first set of RPSTs of the full tree derived from a first subtree (denoted as “X” for the purposes of illustration) may be combined or merged with individual elements of a second set of RSPTs of the tree derived from a second subtree (denoted as “Y” for the purposes of illustration). Here, the elements of X and Y may represent individually enumerated RPSTs of the tree derived from the first and second subtrees, respectively. In a particular embodiment, the elements of X and Y may be represented as natural numerals associated with enumerated RPSTs derived from the respective first and second subtrees (according to an association of trees and natural numerals as illustrated in FIG. 4 , for example). Accordingly, a merger of an RPST represented by an element in X with an RPST represented by an element in Y at the root node of the tree may represented by a multiplication of these natural numerals resulting in a natural numeral representing the RPST resulting from the merger.

According to one embodiment, a merger operation discussed above (e.g., for combining trees at their root nodes to provide a graphical and numerical expression of the resulting merged trees) may be expanded to create a set merger operation to include a merger among RPSTs (e.g., derived from different subtrees as illustrated above). Here, a member RPST of a first set merges with a member RPST of a second set to provide a member of a third, merged set containing the merged RPSTs as elements, for all members of both first and second sets. Regarding the aforementioned representation of the RPSTs as natural numerals, the set merger operation to merge sets X and Y may be expressed as follows:

$\begin{matrix} \begin{matrix} {{X \times Y} = {{\left\{ {x_{1},x_{2},x_{3},\ldots,x_{n}} \right\} \times \left\{ {y_{1},y_{2},y_{3},\ldots,y_{m}} \right\}} =}} \\ {= {\left\{ {{x_{1}*y_{1}},{x_{1}*y_{2}},{x_{1}*y_{3}},\ldots,{x_{1}*y_{m}}} \right\}\bigcup}} \\ {\left\{ {{x_{2}*y_{1}},{x_{2}*y_{2}},{x_{2}*y_{3}},\ldots,{x_{1}*y_{m}}} \right\}\bigcup} \\ {\left\{ {{x_{3}*y_{2}},{x_{3}*y_{2}},{x_{3}*y_{3}},\ldots,{x_{3}*y_{m}}} \right\}\bigcup\ldots\bigcup} \\ \left\{ {{x_{n}*y_{1}},{x_{n}*y_{2}},{x_{n}*y_{3}},\ldots,{y_{n}*y_{m}}} \right\} \end{matrix} & (4) \end{matrix}$

where:

-   -   x₁, x₂, x₃, . . . x_(n) are the natural numerals representing         RPSTs in set X; and     -   y₁, y₂, y₃, . . . y_(m) are the natural numerals representing         RPSTs in set Y;

FIGS. 16, 17 and 18 are flow diagrams illustrating a process to enumerate RPSTs from a full tree which applies the aforementioned push operations, inverse push operation and set merger operation of relations (1) through (4) according to a particular embodiment. FIG. 16 illustrates a process 1600 to receive a natural numeral representing a full tree, FT, at block 1602. Diamond 1604 may determine whether the tree represented by FT comprises an empty tree. In this particular embodiment, the value “r” is zero or one depending on whether a single node tree is associated with a value of zero or one (e.g., depending on a particular association embodiment defined above in connection with the push operation of relation (1)). Here, diamond 1604 determines whether the tree represented by FT is an empty tree based upon whether FT is less than r. However, this is merely an example of a technique to identify an empty tree and the claimed subject matter is not limited in this respect. Process 1600 terminates at block 1612 if diamond 1604 determines that FT represents an empty tree. Diamond 1606 determines whether FT represents a single node tree based upon whether FT equals r. However, this is merely an example of a technique to identify a single node tree and the claimed subject matter is not limited in this respect. If FT comprises a single node tree, block 1608 assigns r as the RPST element of {RPSTs::FT} and the process 1600 terminates at block 1612.

Diamond 1606 determines whether FT comprises two or more nodes by determining whether FT is greater than r. If so, block 1610 may initiate execution of process 1700 shown in FIG. 17 . Block 1704 initializes the set {RPSTs::FT} to contain no elements while execution of the remaining portions of process 1700 may subsequently add elements to this set. As discussed below, process 1700 may be recursively executed to determine, for example, RPSTs of subtrees of the full tree represented by FT. Accordingly, diamond 1706 determines, much like diamond 1606 of process 1600, whether FT (e.g., in a recursive execution) represents a single node tree. If so, then process 1700 (and process 1600) terminate at block 1720.

If FT is greater than r, diamond 1708 determines whether FT represents a tree comprising a single subtree (e.g. comprising a child tree pushed from the full tree node by an edge as shown in FIG. 13 ) or a tree comprising a root node that merges two or more subtrees (e.g., as shown in FIG. 8 ). Here, diamond 1708 determines that FT represents a tree comprising a single subtree if FT comprises a norm-composite numeral, and determines that FT represents a tree having a root node merging two or more subtrees if FT comprises a composite numeral. For this embodiment, an association between trees and natural numerals ay associate composite natural numerals with trees merging two or more subtrees at a root node, and may associate non-composite numerals with trees comprising a single subtree (here, a pushed child tree coupled to the root node of the tree by an edge). However, this is merely an example of an association embodiment, and the claimed subject matter is not limited in this respect.

Similar to the process 1250 illustrated above with reference to FIG. 12 , process 1700 employs a process to enumerate the RPSTs of a full tree based, at least in part, on the configuration of the full tree. Here, it should be observed that block 1710 through 1716 collectively represent a process of enumerating RPSTs of a full tree having a single subtree. Process 1700 may employ a different process at block 1718 if the full tree comprises two or more subtrees merged at a root node. As illustrated below, the RPSTs of a full tree may be determined, at least in part, by an enumeration of RPSTs of child trees of subtrees. Accordingly, the process 1700 of enumerating RPSTs of a full tree may include recursively executed for determining such RPSTs of the child trees.

If diamond 1708 determines that FT represents a tree comprising a single subtree, block 1710 executes an inverse push operation on FT as illustrated above in relation (3) to determine a natural numeral “child” representing the child tree coupled to the root node of the tree represented by FT (and edge label value “j” linking the root node with the child tree). At least some of the RPSTs of the tree represented by FT may be derived from RPSTs of the child tree determined at block 1710. Accordingly, block 1712 may recursively execute process 1700 to enumerate the RPSTs of the child tree ({RPSTs::child}). Here, the recursively executed process may apply the natural numeral “child” representing the child tree (e.g., as determined at block 1710) as the FT input value. Block 1714 then combines the single node tree represented by “r” with the set of enumerated RPSTs determined at block 1712. Block 1716 then performs a push operation according to relation (2) on the elements of this combined set {RPSTs::child} to complete the enumeration of the elements of {RPSTs::FT} in a pushed set with the edge label value “j” determined from the inverse push operation at block 1710.

If diamond 1708 determines that FT represents a tree comprising a root node that merges two or more subtrees, block 1718 may enumerate the elements of {RPSTs::FT} by executing a process 1800 shown in FIG. 18 . As such, block 1718 may provide the composite numeral FT as an input value to process 1800 at block 1802. Subsequent blocks 1804 through 1818 may then enumerate RPSTs for individual subtrees merged at the root node of the tree represented by FT, and determine {RPSTs::FT} from combinations of the RPSTs enumerated from particular ones of the merged subtrees.

A processing loop of blocks 1806 through 1816 incrementally factors the composite numeral FT into non-composite numerals “ST” representing individual subtrees merged at the root node of the tree represented by FT. Again, this particular embodiment includes an association between trees and natural numerals that associates composite natural numerals with trees merging two or more subtrees at a root node and associates non-composite numerals with trees having a root node coupled to a single pushed subtree; however, the claimed subject matter is not limited in scope to this particular embodiment. Here, block 1804 initializes a “remainder” as FT and block 1808 determines the non-composite numeral ST as the smallest non-composite factor of the remainder. If the remainder is decreased to below r, representing a single node tree in this particular embodiment), sequential execution returns to process 1700 at block 1818.

Through successive executions of the processing loop of blocks 1806 through 1816, block 1808 may sequentially factor the numeral FT into non-composite numerals representing subtrees of the tree represented by FT. According to a particular association embodiment, these non-composite numerals may represent individual ones of subtrees merged at a root node of the tree represented by FT. As at least a portion of the RPSTs of the tree represented by FT may be determined from the RSPTs of these subtrees, block 1810 may recursively execute the process 1700 to enumerate the RPSTs of the subtrees represented by the non-composite values ST determined at block 1808.

It should be observed that the elements of {RPSTs::FT} are derived from the RPSTs enumerated from individual subtrees (determined through loop iterations of block 1810). In addition to these elements, {RPSTs::FT} also includes merged combinations of RPSTs derived from RPSTs enumerated from different subtrees at block 1810 in different loop iterations. Through executions of the loop of block 1806 through 1816, block 1812 updates {RPSTs::FT}. By way of example, for the purpose of illustration, in an initial iteration of the loop, block 1812 may merely assign elements to {RPSTs::FT} (which is initialized as the empty set) to include the RPSTs enumerated at block 1810 from a first subtree of the tree represented by FT. In a second iteration of the loop, block 1810 enumerates RPSTs of a second subtree of the tree represented by FT. In addition to adding the enumerated RPSTs of the second subtree to {RPSTs::FT} (updated in the initial loop iteration to include RPSTs enumerated from the first subtree), block 1812 in the second iteration also updates {RPSTs::FT} to include RPSTs formed from the merger of the current individual elements of {RPSTs::FT} (again, updated from the initial iteration) with individual enumerated RPSTs of the second subtree. Here, block 1812 employs a set merger operation according to relation (4) to determine a merger of the current individual elements of {RPSTs::FT} (e.g., assigning the elements of {RPSTs::FT} to “X”) with the individual elements of the enumerated RPSTs of the second subtree (e.g., assigning the elements of RPSTs of the second subtree to “Y”). Subsequent iterations of the processing loop of blocks 1806 through 1816 may then enumerate the RPSTs of additional subtrees, and update {RPSTs::FT} based upon the elements of {RPSTs::FT} updated in the previous iteration and the enumerated RPSTs of the subsequent subtree children in like fashion.

FIGS. 19 through 28 are schematic diagrams of trees illustrating a specific example of enumerating RPSTs of a tree according to the processes of FIGS. 16, 17 and 18 . FIG. 19 shows a tree 1900 which comprises a BELT for this particular illustration of an embodiment, however, it should be understood that the processes described for enumerating RPSTs are applicable to non-BELT trees as well, and that the claimed subject matter is not limited in this respect.

Tree 1900 may be represented as a natural numeral “249” according to an association of trees and natural numerals as described above with reference to FIG. 4 , for example. As tree 1900 comprises two or more subtrees merged at a root node 1902, the natural numeral 249 comprises a non-composite natural numeral. Commencing execution of process 1600 for determining {RPSTs::249}, block 1602 defines FT=249. Since tree 1900 comprises a BELT in this particular embodiment, the value of “r” may be “1” consistent with the application of the push operation of relation (1). Accordingly, diamonds 1604 and 1606 direct initiating execution of process 1700 through block 1610.

Block 1704 initializes {RPSTs::249} as an empty set to be subsequently filled with natural numerals representing RPSTs of tree 1900. Since 249 (here, FT) comprises a composite natural numeral, block 1718 may initiate an instance of process 1800. Block 1804 initializes “remainder”=249 and block 1808 determines ST to be the natural numeral 3 (since 249 may be factored into two non-composite numerals 3 and 83).

Block 1810 may initiate a first recursive instance of process 1700 while providing FT=ST=3 as an input value, diamond 1708 determines that 3 is a non-composite numeral. Block 1710 performs an inverse push operation according to relation (3) to determine a natural numeral representative of the child tree of the subtree corresponding to the natural numeral 3 and an edge label value of an edge linking the child tree with the root node as follows:

$\begin{matrix} \begin{matrix} {{{push}^{- 1}\left( {{r = 1},{k = 2},{{ST} = 3}} \right)} = \left\langle {{child},j} \right\rangle} \\ {{child} = {{Int}\left\lbrack {\left( {{P^{- 1}(3)} + 2 - \left( {2 - 1} \right)} \right)/2} \right\rbrack}} \\ {= {{Int}\left\lbrack {\left( {2 + 2 - \left( {2 - 1} \right)} \right)/2} \right\rbrack}} \\ {= 1} \\ {j = {\left\lbrack \left( {{P^{- 1}(3)} + 2 - \left( {2 - 1} \right)} \right. \right\rbrack{{modulo}\lbrack 2\rbrack}}} \\ {= {\left\lbrack \left( {2 + 2 - \left( {2 - 1} \right)} \right. \right\rbrack{{modulo}\lbrack 2\rbrack}}} \\ {= 1} \end{matrix} & (5) \end{matrix}$

Block 1712 initiates execution of a second recursive instance of process 1700, initializing {RPSTs::child}=0 and terminating at block 1720 through diamond 1706 (since child=1≤r). Returning to block 1714 of the first recursive instance of process 1700, {RPSTs::child} is updated to be {r}={1} for this particular case of a BELT. Block 1716 then performs a push operation on the elements of the set {r} according to relation (2) (applying the edge label value=1 as determined in relation (5) for block 1710) to provide an RPST, {3}, which is graphically illustrated in FIG. 20 .

Execution of the initial instance of process 1800 then returns to block 1812 for updating {RPSTs::FT} by including {RPSTs::ST} (={3} as determined above and merged combinations of the enumerated {RPSTs::ST} with any other previously enumerated RPSTs according to relation (4). Since {RPSTs::FT} at this point comprises an empty set, block 1812 merely updates {RPSTs::FT} to include the single element of {RPSTs::ST}. Block 1814 updates the remainder as FT/ST=249/3=83. This numeral corresponds to a subtree of tree 1900 formed by nodes 1902, 1906, 1908, 1910 and 1912 graphically illustrated as subtree 2100 in FIG. 21 .

On a second iteration of the processing loop of blocks 1806 through 1816, block 1808 determines the non-composite factor of the remainder updated at block 1814 of the first iteration of the processing loop. Here, the natural numeral remainder, 83 as determined at block 1814 in the first iteration, comprises a non-composite numeral. Accordingly, block 1808 determines the natural numeral ST of the current iteration to be 83. Block 1810 then determines {RPSTs::83} by initiating a third recursive instance of process 1700. Since 83 is a non-composite natural numeral (as determined at diamond 1708), block 1710 determines the inverse push of 83 according to relation (3) as follows:

$\begin{matrix} \begin{matrix} {{{push}^{- 1}\left( {{r = 1},{k = 2},{{ST} = 83}} \right)} = \left\langle {{child},j} \right\rangle} \\ {{child} = {{Int}\left\lbrack {\left( {{P^{- 1}(83)} + 2 - \left( {2 - 1} \right)} \right)/2} \right\rbrack}} \\ {= {{Int}\left\lbrack {\left( {23 + 2 - \left( {2 - 1} \right)} \right)/2} \right\rbrack}} \\ {= 12} \\ {j = {\left\lbrack \left( {{P^{- 1}(83)} + 2 - \left( {2 - 1} \right)} \right. \right\rbrack{{modulo}\lbrack 2\rbrack}}} \\ {= {\left\lbrack \left( {23 + 2 - \left( {2 - 1} \right)} \right. \right\rbrack{{modulo}\lbrack 2\rbrack}}} \\ {= 0} \end{matrix} & (6) \end{matrix}$

The result of this inverse push operation is graphically illustrated in FIG. 22 which includes a child tree 2200 of the subtree 2100 formed by the nodes 1906, 1908, 1910 and 1912. Block 1712 then determines {RPSTs::12} by initiating a fourth recursive instance of process 1700 (setting FT=child=12). Since the natural numeral “12” is a composite numeral (representing a tree which merges subtrees at a root node), block 1718 may determine {RPSTs::12} by initiating a first recursive instance of process 1800. As block 1804 sets remainder=“12”, block 1808 determines ST (the natural numeral representing a first merged subtree) as “2.” Block 1810 may then determine {RPSTs::2} by initiating a fifth recursive instance of process 1700. Here, since 2 is a non-composite numeral (as determined at diamond 1708), block 1710 may determine the inverse push of “2” according to relation (3) as follows:

$\begin{matrix} \begin{matrix} {{{push}^{- 1}\left( {{r = 1},{k = 2},{{ST} = 2}} \right)} = \left\langle {{child},j} \right\rangle} \\ {{child} = {{Int}\left\lbrack {\left( {{P^{- 1}(2)} + 2 - \left( {2 - 1} \right)} \right)/2} \right\rbrack}} \\ {= {{Int}\left\lbrack {\left( {1 + 2 - \left( {2 - 1} \right)} \right)/2} \right\rbrack}} \\ {= 1} \\ {j = {\left\lbrack \left( {{P^{- 1}(2)} + 2 - \left( {2 - 1} \right)} \right. \right\rbrack{{modulo}\lbrack 2\rbrack}}} \\ {= {\left\lbrack \left( {1 + 2 - \left( {2 - 1} \right)} \right. \right\rbrack{{modulo}\lbrack 2\rbrack}}} \\ {= 0} \end{matrix} & (7) \end{matrix}$

Block 1712 may initiate a sixth recursive instance of process 1700 to determine {RPSTs::1}. Diamond 1706 of the sixth recursive instance of process 1700 may terminate and return {RPSTs::1}=Ø (i.e., the empty set). Returning to the fifth recursive instance of process 1700, block 1714 updates {RPSTs::child} to include {r} ({r}={1} for this particular case where tree 1200 is a BELT). Accordingly, {RPSTs::2}=push {1}={2} (using the edge label value)=0 as determined at block 1710 of the fifth recursive instance of process 1700 and shown in relation (7)). This corresponds with the RPST 2300 of child tree 2200 formed by node 1906, and either node 1908 or 1912 as shown in FIG. 23 .

Returning to block 1812 of the first recursive instance of process 1800, {RPSTs::12} is updated as {2}. The remainder is updated to be the natural numeral remainder/ST 12/2=6. Block 1808 determines ST to be the smallest non-composite factor of the updated remainder (here, “6”) to be “2.” As illustrated above in the fifth recursive instance of process 1700, block 1810 determines {RPSTs::2} to be {2} (again, corresponding with the RPST of subtree 2200 formed by node 1906, and either node 1908 or 1912). Block 1812 may then determine combinations of the previously enumerated elements of {RPSTs::12} with the elements of {RPSTs::ST} using the set merger operation of relation (4) and update {RPSTs::12} as follows:

$\begin{matrix} \begin{matrix} \left. \left. {\left. {\left\{ {{RPSTs}\text{::}12} \right\} = {\left\{ {{RPSTs}\text{::}12} \right\}\bigcup\left\{ {{RPSTs}\text{::}2} \right\}\bigcup\left\lbrack \left\{ {{RPSTs}\text{::}12} \right. \right.}} \right) \times \left\{ {{RPSTs}\text{::}2} \right.} \right) \right\rbrack \\ {= {\left\{ {{RPSTs}\text{::}2} \right\}\bigcup\left\{ {{RPSTs}\text{::}2} \right\}\bigcup\left\lbrack {\left\{ {{RPSTs}\text{::}2} \right\} \times \left\{ {{RPSTs}\text{::}2} \right\}} \right\rbrack}} \\ {= {\left\{ 2 \right\}\bigcup\left\{ 2 \right\}\bigcup\left\lbrack {\left\{ 2 \right\} \times \left\{ 2 \right\}} \right\rbrack}} \\ {= \left\{ {2,4} \right\}} \end{matrix} & (8) \end{matrix}$

This updated {RPSTs::12} is graphically illustrated in FIGS. 23 (illustrating the RPST 2300 of child tree 2200) and 24 (illustrating an RPST 2400 of subtree 2200 associated with the natural numeral 4).

Block 1814 then updates the remainder=remainder/ST=6/2=3, and the next iteration of the processing loop of blocks 1806 through 1816 determines ST as “3” at block 1808. Block 1810 may determine {RPSTs::ST}={RPSTs::=3}={3} as illustrated above in the first recursive instance of process 1700. This resulting RSPT of the child tree 2200 includes nodes 1906 and 1910 as shown in RPST 2500 of FIG. 25 . Block 1812 then updates {RPSTs::12} (from {RPSTs::12}={2, 4} at relation (8) as follows:

$\begin{matrix} \begin{matrix} {\left\{ {{RPSTs}\text{::}12} \right\} = {\left\{ {2,4} \right\}\bigcup\left\{ 3 \right\}\bigcup\left\lbrack {\left\{ {2,4} \right\} \times \left\{ 3 \right\}} \right\rbrack}} \\ {= {\left\{ {2,3,4} \right\}\bigcup\left\{ {6,12} \right\}}} \\ {= \left\{ {2,3,4,6,12} \right\}} \end{matrix} & (9) \end{matrix}$

The resulting elements of {RPSTs::12} are graphically illustrated in FIG. 26 with corresponding nodes 1906, 1908, 1910 and 1912 of the child tree 2200 shown in FIG. 22 . It should be noted that in the process of enumerating of elements of the set {RPSTs::12} at relations (8) and (9), duplicate RPSTs were enumerated for the RPST corresponding with numeral “4.” Here, in listing the elements of the set {RPSTs::12} at relations (8) and (9) in this particular embodiment such a duplicate listing the RPST corresponding with the numeral “4” was not included so as to provide unique, unordered elements of the set {RPSTs::12}. However, this is merely a particular embodiment provided for illustration and the claimed subject matter is not limited in this respect. For example, it should be readily appreciated that the process of enumerating RPSTs of a tree or subtree described herein may be readily applied alternative embodiments for enumerating RPSTs of a tree or subtree that includes such duplicated RPSTs. Again, this example of enumerating duplicate RPSTs is also merely an example provided for the purpose of illustration and the claimed subject matter is not limited in this respect.

Returning to the third recursive instance of process 1700 (following the identification of 2200 as the child tree of RPST 2100 at block 1710 and the enumeration of the RPSTs of subtree 2200 as the elements of {RPSTs::12} in block 1712}), block 1714 updates {RPSTs::child} to include {RPSTs::12} U {r}={1, 2, 3, 4, 6, 12}. Block 1716 may then complete the enumeration of the elements of {RPSTs::83} by performing a push operation on the elements of {RPSTs::child} according to relation (2) (with label index value j=0 as determined in relation (6)) as follows:

{RPSTs::83}=zero-push({1,2,3,4,0,12})={2,5,11,17,31,83}  (10)

The resulting elements of {RPSTs::83} are graphically illustrated with reference to FIG. 27 with corresponding nodes 1902, 1906, 1908, 1910 and 1912 of the subtree 2100 shown in FIG. 21 .

Returning to the initial instance of process 1800 (following the enumeration of elements in {RPSTs::3} corresponding with a first subtree merged at root node 1902 as graphically illustrated in FIG. 20 and the enumeration of elements in {RPSTs::83} corresponding with a second subtree merged at root node 1902 as graphically illustrated in FIG. 27 ), block 1812 updates {RPSTs::FT} as follows:

$\begin{matrix} \begin{matrix} {\left\{ {{RPSTs}\text{::}{FT}} \right\} = {\left\{ {{RPSTs}\text{::}3} \right\}\bigcup\left\{ {{RPSTs}\text{::}83} \right\}\bigcup\left\lbrack {\left\{ {{RPSTs}\text{::}3} \right\} \times \left\{ {{RPSTs}\text{::}83} \right\}} \right\rbrack}} \\ {= {\left\{ {2,3,5,11,17,31,83} \right\}\bigcup\left\lbrack {\left\{ 3 \right\} \times \left\{ {2,5,11,17,31,83} \right\}} \right\rbrack}} \\ {= {\left\{ {2,3,5,11,17,31,83} \right\}\bigcup\left\{ {6,15,33,51,93,249} \right\}}} \\ {= \left\{ {2,3,5,6,11,15,17,31,33,51,83,93,249} \right\}} \end{matrix} & (11) \end{matrix}$

While the above illustrated example is a specific case of enumerating RPSTs from one particular BELT (associated with the natural numeral 249), it should be understood that the processes are general enough to enumerate RPSTs for any tree. Also, while the illustrated example is specifically directed to enumerating RPSTS of a BELT, the claimed subject matter is not limited to this specific example or specifically to BELTs.

According to an embodiment, the technique described above may have many applications in the management and/or manipulation of hierarchical data. The ability to enumerate possible RPSTs from a tree may be applied to any one of several database management applications. In one example, a complicated tree matching process may be simplified to a more computationally efficient set inclusion process. In a particular example, processing a query to an extensible markup language (XML) document or set of documents may be simplified to a set inclusion process. Here, the XML document or set of documents may be represented as a tree associated with a natural numeral. The RPSTs of the tree may then be enumerated to model possible logical branches of the query through the XML document or set of documents, and enumerated RPSTs are associated with natural numerals in a set of natural numerals representing the possible logical branches. A natural numeral representing the query may then be compared with the elements in the set representing the possible logical branches to determine one or more matches. The query may then be “answered” using the RPSTs associated with the matched elements.

In another particular example applied to biometric pattern recognition, a known biometric pattern (e.g., facial features) may be modeled as a tree associated with a natural numeral. The RPSTs of the tree may then be enumerated to model possible features or combinations of features of the biometric pattern, and the enumerated RPSTs may be associated with natural numerals in a set of natural numerals representing features of the biometric pattern. A natural numeral representing one or more detected features of a subject or specimen may be compared to the elements of the set to determine one or more matches. A positive identification of the subject or specimen may then be determined based, at least in part, upon the one or more matches.

It should be understood that the above described applications of the process for enumerating RPSTs of a tree are merely example applications and that the claimed subject matter is not limited to such example applications.

It should also be understood that, although particular embodiments have just been described, the claimed subject matter is not limited in scope to a particular embodiment or implementation. For example, one embodiment may be in hardware, such as implemented to operate on a device or combination of devices, for example, whereas another embodiment may be in software. Likewise, an embodiment may be implemented in firmware, or as any combination of hardware, software, and/or firmware, for example. Such software and/or firmware may be expressed as machine-readable instructions which are executable by a processor. Likewise, although the claimed subject matter is not limited in scope in this respect, one embodiment may comprise one or more articles, such as a storage medium or storage media. This storage media, such as one or more CD-ROMs and/or disks, for example, may have stored thereon instructions, that when executed by a system, such as a computer system, computing platform, or other system, for example, may result in an embodiment of a method in accordance with the claimed subject matter being executed, such as one of the embodiments previously described for example. As one potential example, a computing platform may include one or more processing units or processors, one or more input/output devices, such as a display, a keyboard and/or a mouse, and/or one or more memories, such as static random access memory, dynamic random access memory, flash memory, and/or a hard drive, although, again, the claimed subject matter is not limited in scope to this example.

In the preceding description, various aspects of the claimed subject matter have been described. For purposes of explanation, specific numbers, systems and/or configurations were set forth to provide a thorough understanding of the claimed subject matter. However, it should be apparent to one skilled in the art having the benefit of this disclosure that the claimed subject matter may be practiced without the specific details. In other instances, well-known features were omitted and/or simplified so as not to obscure the claimed subject matter. While certain features have been illustrated and/or described herein, many modifications, substitutions, changes and/or equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and/or changes as fall within the true spirit of the claimed subject matter. 

1-56. (canceled)
 57. A method, comprising: representing content, at least in part, as a data representation that comprises a set of partial subtrees, wherein the set of partial subtrees comprises at least a first partial subtree having a same node as a second partial subtree; representing a query as a numeral; comparing the numeral with one or more numerals to generate a result; enumerating the set of partial subtrees, wherein the one or more numerals represent the enumerated set of partial subtrees; and returning at least one or more corresponding partial subtrees of the enumerated set of partial subtrees based, at least in part, on the result of the comparing.
 58. The method of claim 57, wherein the data representation is a complex tree hierarchy.
 59. The method of claim 57, wherein the data representation is a multi-dimensional data representation.
 60. The method of claim 57, further comprising: identifying one or more subtrees coupled to a root node of the data representation; and wherein the enumerating, comprises: enumerating the set of partial subtrees of the one or more subtrees that is identified.
 61. The method of claim 60, further comprising: merging combinations of individual ones of the enumerated set of partial subtrees of the one or more subtrees that is identified.
 62. The method of claim 61, wherein the data representation is represented as a composite numeral, and wherein the identifying the one or more subtrees further comprises: factoring the composite numeral.
 63. The method of claim 57, wherein the data representation comprises: an edge labeled tree or a node labeled tree.
 64. The method of claim 57, wherein the at least one or more corresponding partial subtrees of the set of partial subtrees are returned in response to the query.
 65. The method of claim 57, wherein the data representation is represented, at least in part, via a hierarchical set of stored states, and wherein the set of partial subtrees represent at least a portion of the hierarchical set of stored states in the data representation.
 66. The method of claim 57, wherein the enumerated set of partial subtrees of the data representation comprises at least one of: an empty tree; a single node tree; a tree comprising a subtree coupled to a root node of the data representation by an edge; or two or more trees coupled to a root node of the data representation by respective edges.
 67. An apparatus, comprising: at least one computing device including at least one processor configured to: represent content, at least in part, as a data representation that comprises a set of partial subtrees, wherein the set of partial subtrees to comprises at least a first partial subtree to have a same node as a second partial subtree; represent a query as a numeral; compare the numeral with one or more numerals to generate a result; enumerate the set of partial subtrees, wherein the one or more numerals represent the enumerated set of partial subtrees; and return at least one or more corresponding partial subtrees of the enumerated set of partial subtrees based, at least in part, on the result of comparing the numeral with one or more numerals.
 68. The apparatus of claim 67, wherein the at least one processor is further configured to: identify one or more subtrees to be coupled to a root node of the data representation; and enumerate the set of partial subtrees of the one or more subtrees that is identified.
 69. The apparatus of claim 68, wherein the at least one processor is further configured to: merge combinations of individual ones of the enumerated set of partial subtrees of the one or more subtrees that is identified.
 70. The apparatus of claim 69, wherein the data representation is to be represented as a composite numeral, and wherein the processor is further configured to: factor the composite numeral.
 71. The apparatus of claim 67, wherein the data representation is to be represented, at least in part, via a hierarchical set of stored states, and wherein the set of partial subtrees to represent at least a portion of a set of stored states in the data representation.
 72. The apparatus of claim 67, wherein the enumerated set of partial subtrees of the data representation to comprise at least one of: an empty tree; a single node tree; a tree that comprises a subtree to be coupled to a root node of the data representation by an edge; or two or more trees to be coupled to a root node of the data representation by respective edges.
 73. An article comprising: a non-transitory storage medium having machine-readable instructions stored thereon executable by at least one computing device comprising at least one processor to: represent content, at least in part, as a data representation that comprises a set of partial subtrees, wherein the set of partial subtrees to comprises at least a first partial subtree to have a same node as a second partial subtree; represent a query as a numeral; compare the numeral with one or more numerals to generate a result; enumerate the set of partial subtrees, wherein the one or more numerals represent the enumerated set of partial subtrees; and return at least one or more corresponding partial subtrees of the enumerated set of partial subtrees based, at least in part, on the result of comparing the numeral with one or more numerals.
 74. The article of claim 73, wherein the non-transitory storage medium further comprises machine-readable instructions stored thereon to: identify one or more subtrees to be coupled to a root node of the data representation; and enumerate the set of partial subtrees of the one or more subtrees that is identified.
 75. The article of claim 74, wherein the non-transitory storage medium further comprises machine-readable instructions stored thereon to: merge combinations of individual ones of the enumerated set of partial subtrees of the one or more subtrees that is identified.
 76. The article of claim 75, wherein the data representation is to be represented as a composite numeral, and wherein the non-transitory storage medium further comprises machine-readable instructions stored thereon to: factor the composite numeral. 